-
Notifications
You must be signed in to change notification settings - Fork 516
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
⬆️ Update pytest-asyncio to 0.23.4 #2764
⬆️ Update pytest-asyncio to 0.23.4 #2764
Conversation
@dbluhm I know there are likely other priorities to focus on, but just want to raise this one as a potentially important fix, to get the test framework up to date before the 1.0.0 release. Technically just a "nice to have" to make test logs and other warnings easier to review I'm not so sure how to tackle this one yet, so I wanted to ask if you have any insight as to what might be necessary here. If it's not apparent then it's no worries, I'll take a deeper look once some bandwidth has freed up |
I agree that taking care of the deprecation warnings is valuable, if only to make developers lives easier. Thanks for your efforts on that front (with this and past PRs)! Yeah, unfortunately, off the rip, nothing immediately stands out to me as to what might be causing these test failures. |
Signed-off-by: ff137 <[email protected]>
Signed-off-by: ff137 <[email protected]>
Signed-off-by: ff137 <[email protected]>
Signed-off-by: ff137 <[email protected]>
Signed-off-by: ff137 <[email protected]>
Signed-off-by: ff137 <[email protected]>
Signed-off-by: ff137 <[email protected]>
Signed-off-by: ff137 <[email protected]>
cfc4b5b
to
c69c713
Compare
@dbluhm all good! I think I got to the bottom of it... Some tests needed to be marked for skip, requiring bbs or askar. One test (test_fix_ledger) requires indy_credx to work, but I could re-mock it to work without skipping it. And some tests required higher event loop scope. Not sure why, but that solves it! So I think this successfully upgrades to latest pytest-asyncio release, and resolves ~2100 warnings <:-). Just 245 to go 😂 Please review and see if it's all in order! |
Signed-off-by: ff137 <[email protected]>
Quality Gate passedKudos, no new issues were introduced! 0 New issues |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Summary:
⬆️ Upgrades pytest-asyncio to latest
✅ fix some test's event loop scopes (also mark some tests requiring askar or bbs)
🎉 resolves 2154 deprecation warnings
Original:
Reviewing test logs show that there are 2154 deprecation warnings coming from across 202 test files, each reporting:
This indicates that the pytests are not configured correctly, or at least not in an up-to-date way.
These are the current test results after upgrading to the latest pytest-asyncio version
Edit: these new test failures/errors all come down to either pytest scope needing to be a higher level, or tests that should be marked "to skip" (askar or bbs)